Downlink and Uplink Channel Transmission and Monitoring in a Wireless Network

ABSTRACT

A wireless device may receive one or more radio resource control (RRC) messages comprising configuration parameters for one or more unlicensed cells. The wireless device may selectively monitor a downlink physical control channel (PDCCH) on one of the unlicensed cells, depending on whether there is an uplink transmission or downlink transmission on another unlicensed cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/749,773, filed on Jan. 22, 2020, which is a continuation of U.S. application Ser. No. 15/419,445, filed on Jan. 30, 2017, now U.S. Pat. No. 10,548,121, which claims the benefit of U.S. Provisional Application No. 62/290,691, filed on Feb. 3, 2016, each of which is hereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers in a carrier group as per an aspect of an embodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per an aspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wireless device as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC as per an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC as per an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram depicting a downlink burst as per an aspect of an embodiment of the present disclosure.

FIG. 11 is an example diagram depicting a plurality of cells as per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting a plurality of cells as per an aspect of an embodiment of the present disclosure.

FIG. 13 is an example diagram depicting a plurality of cells as per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram depicting a plurality of cells as per an aspect of an embodiment of the present disclosure.

FIG. 15 is an example diagram depicting a plurality of cells as per an aspect of an embodiment of the present disclosure.

FIG. 16 is an example diagram depicting a timing advance as per an aspect of an embodiment of the present disclosure.

FIG. 17 is an example flow diagram as per an aspect of an embodiment of the present disclosure.

FIG. 18 is an example flow diagram as per an aspect of an embodiment of the present disclosure.

FIG. 19 is an example flow diagram as per an aspect of an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of carrier aggregation. Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LAA licensed assisted access

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the disclosure may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure. As illustrated in this example, arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 shows a subcarrier transmitting information symbols. FIG. 1 is for illustration purposes, and a typical multicarrier OFDM system may include more subcarriers in a carrier. For example, the number of subcarriers in a carrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmission band. As illustrated in FIG. 1, guard band 106 is between subcarriers 103 and subcarriers 104. The example set of subcarriers A 102 includes subcarriers 103 and subcarriers 104. FIG. 1 also illustrates an example set of subcarriers B 105. As illustrated, there is no guard band between any two subcarriers in the example set of subcarriers B 105. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers as per an aspect of an embodiment of the present disclosure. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 10 carriers. Carrier A 204 and carrier B 205 may have the same or different timing structures. Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B 205 may or may not be synchronized with each other. Different radio frame structures may be supported for FDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing. Downlink and uplink transmissions may be organized into radio frames 201. In this example, the radio frame duration is 10 msec. Other frame durations, for example, in the range of 1 to 100 msec may also be supported. In this example, each 10 ms radio frame 201 may be divided into ten equally sized subframes 202. Other subframe durations such as 0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) may consist of two or more slots (for example, slots 206 and 207). For the example of FDD, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in each 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols 203. The number of OFDM symbols 203 in a slot 206 may depend on the cyclic prefix length and subcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present disclosure. The resource grid structure in time 304 and frequency 305 is illustrated in FIG. 3. The quantity of downlink subcarriers or RBs (in this example 6 to 100 RBs) may depend, at least in part, on the downlink transmission bandwidth 306 configured in the cell. The smallest radio resource unit may be called a resource element (e.g. 301). Resource elements may be grouped into resource blocks (e.g. 302). Resource blocks may be grouped into larger radio resources called Resource Block Groups (RBG) (e.g. 303). The transmitted signal in slot 206 may be described by one or several resource grids of a plurality of subcarriers and a plurality of OFDM symbols. Resource blocks may be used to describe the mapping of certain physical channels to resource elements. Other pre-defined groupings of physical resource elements may be implemented in the system depending on the radio technology. For example, 24 subcarriers may be grouped as a radio block for a duration of 5 msec. In an illustrative example, a resource block may correspond to one slot in the time domain and 180 kHz in the frequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure. FIG. 5A shows an example uplink physical channel The baseband signal representing the physical uplink shared channel may perform the following processes. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. The functions may comprise scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding of the complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain DFTS-OFDMS/SC-FDMA signal for each antenna port, and/or the like.

Example modulation and up-conversion to the carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna port and/or the complex-valued PRACH baseband signal is shown in FIG. 5B. Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. The baseband signal representing a downlink physical channel may perform the following processes. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. The functions include scrambling of coded bits in each of the codewords to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on each layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for each antenna port to resource elements; generation of complex-valued time-domain OFDM signal for each antenna port, and/or the like.

Example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for each antenna port is shown in FIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wireless device 406, as per an aspect of an embodiment of the present disclosure. A communication network 400 may include at least one base station 401 and at least one wireless device 406. The base station 401 may include at least one communication interface 402, at least one processor 403, and at least one set of program code instructions 405 stored in non-transitory memory 404 and executable by the at least one processor 403. The wireless device 406 may include at least one communication interface 407, at least one processor 408, and at least one set of program code instructions 410 stored in non-transitory memory 409 and executable by the at least one processor 408. Communication interface 402 in base station 401 may be configured to engage in communication with communication interface 407 in wireless device 406 via a communication path that includes at least one wireless link 411. Wireless link 411 may be a bi-directional link. Communication interface 407 in wireless device 406 may also be configured to engage in a communication with communication interface 402 in base station 401. Base station 401 and wireless device 406 may be configured to send and receive data over wireless link 411 using multiple frequency carriers. According to aspects of an embodiments, transceiver(s) may be employed. A transceiver is a device that includes both a transmitter and receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in communication interface 402, 407 and wireless link 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. A software interface may include code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. A firmware interface may include a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics in the device, whether the device is in an operational or non-operational state.

According to various aspects of an embodiment, an LTE network may include a multitude of base stations, providing a user plane PDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towards the wireless device. The base station(s) may be interconnected with other base station(s) (for example, interconnected employing an X2 interface). Base stations may also be connected employing, for example, an S1 interface to an EPC. For example, base stations may be interconnected to the MME employing the S1-MME interface and to the S-G) employing the S1-U interface. The S1 interface may support a many-to-many relation between MMEs/Serving Gateways and base stations. A base station may include many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At RRC connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g. TAI), and at RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell may be the Downlink Primary Component Carrier (DL PCC), while in the uplink, the carrier corresponding to the PCell may be the Uplink Primary Component Carrier (UL PCC). Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with the PCell a set of serving cells. In the downlink, the carrier corresponding to an SCell may be a Downlink Secondary Component Carrier (DL SCC), while in the uplink, it may be an Uplink Secondary Component Carrier (UL SCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to only one cell. The cell ID or Cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used). In the specification, cell ID may be equally referred to a carrier ID, and cell index may be referred to carrier index. In implementation, the physical cell ID or cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. For example, when the specification refers to a first physical cell ID for a first downlink carrier, the specification may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may apply, for example, to carrier activation. When the specification indicates that a first carrier is activated, the specification may also mean that the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on its wireless device category and/or capability(ies). A base station may comprise multiple sectors. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices perform based on older releases of LTE technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CA and DC as per an aspect of an embodiment of the present disclosure. E-UTRAN may support Dual Connectivity (DC) operation whereby a multiple RX/TX UE in RRC_CONNECTED may be configured to utilize radio resources provided by two schedulers located in two eNBs connected via a non-ideal backhaul over the X2 interface. eNBs involved in DC for a certain UE may assume two different roles: an eNB may either act as an MeNB or as an SeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanisms implemented in DC may be extended to cover more than two eNBs. FIG. 7 illustrates one example structure for the UE side MAC entities when a Master Cell Group (MCG) and a Secondary Cell Group (SCG) are configured, and it may not restrict implementation. Media Broadcast Multicast Service (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses may depend on how the bearer is setup. Three alternatives may exist, an MCG bearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may be located in MeNB and SRBs may be configured as a MCG bearer type and may use the radio resources of the MeNB. DC may also be described as having at least one bearer configured to use radio resources provided by the SeNB. DC may or may not be configured/implemented in example embodiments of the disclosure.

In the case of DC, the UE may be configured with two MAC entities: one MAC entity for MeNB, and one MAC entity for SeNB. In DC, the configured set of serving cells for a UE may comprise two subsets: the Master Cell Group (MCG) containing the serving cells of the MeNB, and the Secondary Cell Group (SCG) containing the serving cells of the SeNB. For a SCG, one or more of the following may be applied. At least one cell in the SCG may have a configured UL CC and one of them, named PSCell (or PCell of SCG, or sometimes called PCell), may be configured with PUCCH resources. When the SCG is configured, there may be at least one SCG bearer or one Split bearer. Upon detection of a physical layer problem or a random access problem on a PSCell, or the maximum number of RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: a RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of the SCG may be stopped, and a MeNB may be informed by the UE of a SCG failure type. For split bearer, the DL data transfer over the MeNB may be maintained. The RLC AM bearer may be configured for the split bearer. Like a PCell, a PSCell may not be de-activated. A PSCell may be changed with a SCG change (for example, with a security key change and a RACH procedure), and/or neither a direct bearer type change between a Split bearer and a SCG bearer nor simultaneous configuration of a SCG and a Split bearer may be supported.

With respect to the interaction between a MeNB and a SeNB, one or more of the following principles may be applied. The MeNB may maintain the RRM measurement configuration of the UE and may, (for example, based on received measurement reports or traffic conditions or bearer types), decide to ask a SeNB to provide additional resources (serving cells) for a UE. Upon receiving a request from the MeNB, a SeNB may create a container that may result in the configuration of additional serving cells for the UE (or decide that it has no resource available to do so). For UE capability coordination, the MeNB may provide (part of) the AS configuration and the UE capabilities to the SeNB. The MeNB and the SeNB may exchange information about a UE configuration by employing RRC containers (inter-node messages) carried in X2 messages. The SeNB may initiate a reconfiguration of its existing serving cells (for example, a PUCCH towards the SeNB). The SeNB may decide which cell is the PSCell within the SCG. The MeNB may not change the content of the RRC configuration provided by the SeNB. In the case of a SCG addition and a SCG SCell addition, the MeNB may provide the latest measurement results for the SCG cell(s). Both a MeNB and a SeNB may know the SFN and subframe offset of each other by OAM, (for example, for the purpose of DRX alignment and identification of a measurement gap). In an example, when adding a new SCG SCell, dedicated RRC signaling may be used for sending required system information of the cell as for CA, except for the SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Serving cells in one TAG may use the same timing reference. For a given TAG, user equipment (UE) may use at least one downlink carrier as a timing reference. For a given TAG, a UE may synchronize uplink subframe and frame transmission timing of uplink carriers belonging to the same TAG. In an example, serving cells having an uplink to which the same TA applies may correspond to serving cells hosted by the same receiver. A UE supporting multiple TAs may support two or more TA groups. One TA group may contain the PCell and may be called a primary TAG (pTAG). In a multiple TAG configuration, at least one TA group may not contain the PCell and may be called a secondary TAG (sTAG). In an example, carriers within the same TA group may use the same TA value and/or the same timing reference. When DC is configured, cells belonging to a cell group (MCG or SCG) may be grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present disclosure. In Example 1, pTAG comprises a PCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group (MCG or SCG) and other example TAG configurations may also be provided. In various examples in this disclosure, example mechanisms are described for a pTAG and an sTAG. Some of the example mechanisms may be applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order for an activated SCell. This PDCCH order may be sent on a scheduling cell of this SCell. When cross carrier scheduling is configured for a cell, the scheduling cell may be different than the cell that is employed for preamble transmission, and the PDCCH order may include an SCell index. At least a non-contention based RA procedure may be supported for SCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present disclosure. An eNB transmits an activation command 600 to activate an SCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCH order 601 on an SCell belonging to an sTAG. In an example embodiment, preamble transmission for SCells may be controlled by the network using PDCCH format 1A. Msg2 message 603 (RAR: random access response) in response to the preamble transmission on the SCell may be addressed to RA-RNTI in a PCell common search space (CSS). Uplink packets 604 may be transmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achieved through a random access procedure. This may involve a UE transmitting a random access preamble and an eNB responding with an initial TA command NTA (amount of timing advance) within a random access response window. The start of the random access preamble may be aligned with the start of a corresponding uplink subframe at the UE assuming NTA=0. The eNB may estimate the uplink timing from the random access preamble transmitted by the UE. The TA command may be derived by the eNB based on the estimation of the difference between the desired UL timing and the actual UL timing. The UE may determine the initial uplink transmission timing relative to the corresponding downlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a serving eNB with RRC signaling. The mechanism for TAG configuration and reconfiguration may be based on RRC signaling. According to various aspects of an embodiment, when an eNB performs an SCell addition configuration, the related TAG configuration may be configured for the SCell. In an example embodiment, an eNB may modify the TAG configuration of an SCell by removing (releasing) the SCell and adding(configuring) a new SCell (with the same physical cell ID and frequency) with an updated TAG ID. The new SCell with the updated TAG ID may initially be inactive subsequent to being assigned the updated TAG ID. The eNB may activate the updated new SCell and start scheduling packets on the activated SCell. In an example implementation, it may not be possible to change the TAG associated with an SCell, but rather, the SCell may need to be removed and a new SCell may need to be added with another TAG. For example, if there is a need to move an SCell from an sTAG to a pTAG, at least one RRC message, (for example, at least one RRC reconfiguration message), may be send to the UE to reconfigure TAG configurations by releasing the SCell and then configuring the SCell as a part of the pTAG. Wwhen an SCell is added/configured without a TAG index, the SCell may be explicitly assigned to the pTAG. The PCell may not change its TA group and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (for example, to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells). If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the UE may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the UE may perform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted on the PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE may transmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregated carriers increase, the number of PUCCHs and also the PUCCH payload size may increase. Accommodating the PUCCH transmissions on the PCell may lead to a high PUCCH load on the PCell. A PUCCH on an SCell may be introduced to offload the PUCCH resource from the PCell. More than one PUCCH may be configured for example, a PUCCH on a PCell and another PUCCH on an SCell. In the example embodiments, one, two or more cells may be configured with PUCCH resources for transmitting CSI/ACK/NACK to a base station. Cells may be grouped into multiple PUCCH groups, and one or more cell within a group may be configured with a PUCCH. In an example configuration, one SCell may belong to one PUCCH group. SCells with a configured PUCCH transmitted to a base station may be called a PUCCH SCell, and a cell group with a common PUCCH resource transmitted to the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer may be used to control how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned. The MAC entity may, when a Timing Advance Command MAC control element is received, apply the Timing Advance Command for the indicated TAG; start or restart the timeAlignmentTimer associated with the indicated TAG. The MAC entity may, when a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG and/orif the Random Access Preamble was not selected by the MAC entity, apply the Timing Advance Command for this TAG and start or restart the timeAlignmentTimer associated with this TAG. Otherwise, if the timeAlignmentTimer associated with this TAG is not running, the Timing Advance Command for this TAG may be applied and the timeAlignmentTimer associated with this TAG started. When the contention resolution is considered not successful, a timeAlignmentTimer associated with this TAG may be stopped. Otherwise, the MAC entity may ignore the received Timing Advance Command.

In example embodiments, a timer is running once it is started, until it is stopped or until it expires; otherwise it may not be running A timer can be started if it is not running or restarted if it is running For example, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation of multi-carrier communications. Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of multi-carrier communications. Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a device (e.g. wireless communicator, UE, base station, etc.) to enable operation of multi-carrier communications. The device may include processors, memory, interfaces, and/or the like. Other example embodiments may comprise communication networks comprising devices such as base stations, wireless devices (or user equipment: UE), servers, switches, antennas, and/or the like.

The amount of data traffic carried over cellular networks is expected to increase for many years to come. The number of users/devices is increasing and each user/device accesses an increasing number and variety of services, e.g. video delivery, large files, images. This may require not only high capacity in the network, but also provisioning very high data rates to meet customers' expectations on interactivity and responsiveness. More spectrum may therefore needed for cellular operators to meet the increasing demand. Considering user expectations of high data rates along with seamless mobility, it may be beneficial that more spectrum be made available for deploying macro cells as well as small cells for cellular systems.

Striving to meet the market demands, there has been increasing interest from operators in deploying some complementary access utilizing unlicensed spectrum to meet the traffic growth. This is exemplified by the large number of operator-deployed Wi-Fi networks and the 3GPP standardization of LTE/WLAN interworking solutions. This interest indicates that unlicensed spectrum, when present, may be an effective complement to licensed spectrum for cellular operators to help addressing the traffic explosion in some scenarios, such as hotspot areas. LAA may offer an alternative for operators to make use of unlicensed spectrum while managing one radio network, thus offering new possibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment) may be implemented for transmission in an LAA cell. In a listen-before-talk (LBT) procedure, equipment may apply a clear channel assessment (CCA) check before using the channel. For example, the CCA may utilize at least energy detection to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear, respectively. For example, European and Japanese regulations mandate the usage of LBT in the unlicensed bands. Apart from regulatory requirements, carrier sensing via LBT may be one way for fair sharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensed carrier with limited maximum transmission duration may be enabled. Some of these functions may be supported by one or more signals to be transmitted from the beginning of a discontinuous LAA downlink transmission. Channel reservation may be enabled by the transmission of signals, by an LAA node, after gaining channel access via a successful LBT operation, so that other nodes that receive the transmitted signal with energy above a certain threshold sense the channel to be occupied. Functions that may need to be supported by one or more signals for LAA operation with discontinuous downlink transmission may include one or more of the following: detection of the LAA downlink transmission (including cell identification) by UEs, time & frequency synchronization of UEs, and/or the like.

In an example embodiment, a DL LAA design may employ subframe boundary alignment according to LTE-A carrier aggregation timing relationships across serving cells aggregated by CA. This may not imply that the eNB transmissions can start only at the subframe boundary. LAA may support transmitting PDSCH when not all OFDM symbols are available for transmission in a subframe according to LBT. Delivery of necessary control information for the PDSCH may also be supported.

An LBT procedure may be employed for fair and friendly coexistence of LAA with other operators and technologies operating in an unlicensed spectrum. LBT procedures on a node attempting to transmit on a carrier in an unlicensed spectrum may require the node to perform a clear channel assessment to determine if the channel is free for use. An LBT procedure may involve at least energy detection to determine if the channel is being used. For example, regulatory requirements in some regions, for example, in Europe, may specify an energy detection threshold such that if a node receives energy greater than this threshold, the node assumes that the channel is not free. While nodes may follow such regulatory requirements, a node may optionally use a lower threshold for energy detection than that specified by regulatory requirements. In an example, LAA may employ a mechanism to adaptively change the energy detection threshold. For example, LAA may employ a mechanism to adaptively lower the energy detection threshold from an upper bound. Adaptation mechanism(s) may not preclude static or semi-static setting of the threshold. In an example a Category 4 LBT mechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, for some signals, in some implementation scenarios, in some situations, and/or in some frequencies, no LBT procedure may performed by the transmitting entity. In an example, Category 2 (for example, LBT without random back-off) may be implemented. The duration of time that the channel is sensed to be idle before the transmitting entity transmits may be deterministic. In an example, Category 3 (for example, LBT with random back-off with a contention window of fixed size) may be implemented. The LBT procedure may have the following procedure as one of its components. The transmitting entity may draw a random number N within a contention window. The size of the contention window may be specified by the minimum and maximum value of N. The size of the contention window may be fixed. The random number N may be employed in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel. In an example, Category 4 (for example, LBT with random back-off with a contention window of variable size) may be implemented. The transmitting entity may draw a random number N within a contention window. The size of the contention window may be specified by a minimum and maximum value of N. The transmitting entity may vary the size of the contention window when drawing the random number N. The random number N may be employed in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be different from the DL LBT scheme (for example, by using different LBT mechanisms or parameters), since the LAA UL may be based on scheduled access which affects a UE's channel contention opportunities. Other considerations motivating a different UL LBT scheme include, but are not limited to, multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmission from a DL transmitting node with no transmission immediately before or after from the same node on the same CC. A UL transmission burst from a UE perspective may be a continuous transmission from a UE with no transmission immediately before or after from the same UE on the same CC. In an example, a UL transmission burst may be defined from a UE perspective. In an example, a UL transmission burst may be defined from an eNB perspective. In an example, in case of an eNB operating DL+UL LAA over the same unlicensed carrier, DL transmission burst(s) and UL transmission burst(s) on LAA may be scheduled in a TDM manner over the same unlicensed carrier. For example, an instant in time may be part of a DL transmission burst or an UL transmission burst.

In an example embodiment, in an unlicensed cell, a downlink burst may be started in a subframe. When an eNB accesses the channel, the eNB may transmit for a duration of one or more subframes. The duration may depend on a maximum configured burst duration in an eNB, the data available for transmission, and/or eNB scheduling algorithm. FIG. 10 shows an example downlink burst in an unlicensed (e.g. licensed assisted access) cell. The maximum configured burst duration in the example embodiment may be configured in the eNB. An eNB may transmit the maximum configured burst duration to a UE employing an RRC configuration message.

The wireless device may receive from a base station at least one message (for example, an RRC) comprising configuration parameters of a plurality of cells. The plurality of cells may comprise at least one license cell and at least one unlicensed (for example, an LAA cell). The configuration parameters of a cell may, for example, comprise configuration parameters for physical channels, (for example, a ePDCCH, PDSCH, PUSCH, PUCCH and/or the like).

In an example embodiments, LTE transmission time may include frames, and a frame may include many subframes. The size of various time domain fields in the time domain may be expressed as a number of time units T_(s)=1/(15000×2048)seconds. Downlink, uplink and sidelink transmissions may be organized into radio frames with T_(f)307200×T_(s)=10 ms duration.

In an example LTE implementation, at least three radio frame structures may be supported: Type 1, applicable to FDD, Type 2, applicable to TDD, Type 3, applicable to LAA secondary cell operation. LAA secondary cell operation applies to frame structure type 3.

Transmissions in multiple cells may be aggregated where one or more secondary cells may be used in addition to the primary cell. In case of multi-cell aggregation, different frame structures may be used in the different serving cells.

Frame structure type 1 may be applicable to both full duplex and half duplex FDD. A radio frame is T_(f)=307200·T_(s)=10 ms long and may comprise 20 slots of length T_(slot)=15360·T_(s)=0.5 ms, numbered from 0 to 19. A subframe may include two consecutive slots where subframe i comprises of slots 2 i and 2 i+1.

For FDD, 10 subframes are available for downlink transmission and 10 subframes are available for uplink transmissions in a 10 ms interval. Uplink and downlink transmissions are separated in the frequency domain. In half-duplex FDD operation, the UE may not transmit and receive at the same time while there may not be such restrictions in full-duplex FDD.

Frame structure type 2 may be applicable to TDD. A radio frame of length T_(f)=307200·T_(s)=10 ms may comprise of two half-frames of length 153600·T_(s)=5 ms. A half-frame may comprise five subframes of length 30720·T_(s)=1 ms. A subframe i may comprise two slots, 2 i and 2 i+1, of length T_(slot)=15360·T_(s)=0.5 ms.

The uplink-downlink configuration in a cell may vary between frames and controls in which subframes uplink or downlink transmissions may take place in the current frame. The uplink-downlink configuration in the current frame is obtained via control signaling.

An example subframe in a radio frame, “may be a downlink subframe reserved for downlink transmissions, may be an uplink subframe reserved for uplink transmissions or may be a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS are subject to the total length of DwPTS, GP and UpPTS being equal to 30720·T^(s)=1 ms.

Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity may be supported. In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe may exist in both half-frames. In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe may exist in the first half-frame.

Subframes 0 and 5 and DwPTS may be reserved for downlink transmission. UpPTS and the subframe immediately following the special subframe may be reserved for uplink transmission.

In an example, in case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the cells using frame structure Type 2 have an overlap of at least 1456·T_(s).

In an example, in case multiple cells with different uplink-downlink configurations in the current radio frame are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the following constraints may apply. if the subframe in the primary cell is a downlink subframe, the UE may not transmit any signal or channel on a secondary cell in the same subframe. If the subframe in the primary cell is an uplink subframe, the UE may not be expected to receive any downlink transmissions on a secondary cell in the same subframe. If the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink subframe, the UE may not be expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the same subframe, and the UE may not be expected to receive any other signals on the secondary cell in OFDM symbols that overlaps with the guard period or UpPTS in the primary cell.

Frame structure type 3 may be applicable to LAA secondary cell operation with normal cyclic prefix. A radio frame is T_(f)=307200·T_(s)=10 ms long and comprises of 20 slots of length T_(slot)=15360·T_(s)=0.5 ms, numbered from 0 to 19. A subframe may comprise as two consecutive slots where subframe i comprises slots 2 i and 2 i+1.

The 10 subframes within a radio frame are available for downlink transmissions. Downlink transmissions occupy one or more consecutive subframes, starting anywhere within a subframe and ending with the last subframe either fully occupied or following one of the DwPTS durations. Subframes may be available for uplink transmission when LAA uplink is supported.

In an LAA cell, uplink transmission timing is advanced by N_TA as shown in FIG. 16. A UE advances its transmission timing based on TAC received from the eNB, e.g. to compensate for round-trip propagation delay. This may imply that from a UE transmitter uplink subframe timing starts and ends earlier than downlink subframes. A guard period is needed when downlink transmission ends and uplink transmission starts in a UE. The eNB may not be able to calculate the exact N_TA amount, since the UE may autonomously change the N_TA in some scenarios. A guard period may be required so that uplink and downlink transmission timings do not overlap in a TDD system. In addition, LBT period for a UE may create a transmission gap between downlink transmission and uplink transmission. FIG. 11 shows an example uplink and downlink timings in a UE.

In an example embodiment, the guard period/LBT may provide a transmission gap. Other UEs/nodes (e.g. Wifi nodes) may acquire the channel after downlink transmission ends, and during the transmission/LBT gap. This may not allow a UE to acquire the channel and transmit uplink signals when the UE is granted an uplink resource after a downlink burst. Transmission of reservation signals by a UE may enable to reserve the channel and reduce the possibility of losing a channel

In an LAA system, when an eNB transmits a full downlink subframe, the next available subframe for uplink transmission may be a partial uplink subframe due to transmission gap, NTA requirements, and/or LBT process. In an LAA system, when an eNB transmits an end partial downlink subframe, the next available subframe for uplink transmission may be a full or partial uplink subframe due to transmission gap, NTA requirements, and/or LBT.

In an example implementation, cells in a first group of multiple LAA cells may be aggregated and a UE may not be capable of simultaneous reception and transmission in the aggregated LAA cells. For example, the cells may be in the same band. For example, the cells may be in adjacent frequencies in the same band. This may be due to a software and/or hardware limitation in the wireless device.

Some or all of the cells in the first group of the multiple LAA cells may be capable of simultaneous reception and transmission with the PCell and/or other licensed cells. For example, an LAA cell in the first group may be able to transmit signals while receiving signals on a PCell. In this case, applying constraints to the UE on transmission and reception of signals on LAA based on the state of the PCell (downlink, uplink, or special subframe) seems to be an inefficient and sub-optimal solution.

In an example, a second group of multiple LAA cells different from the first group may be configured. The second group of multiple LAA cells may be aggregated and a UE may not be capable of simultaneous reception and transmission in the aggregated LAA cells of the second group. For example, the cells in the same cell group may be in the same band. For example, the cells may be adjacent in frequency in the same band.

A cell in the first group may transmit signals while a cell in the second group is receiving signals, and vice versa. For example, cells in the first group may be in a first band and the cells in the second group may be in a second band. For example, cells in the first group may employ a first transceiver and cells in the second group may employ a second transceiver. The example embodiments may separately apply to a first group and a second group.

In an example implementation, the cells in the first group may be have their own limitations with respect to simultaneous reception and transmission in the aggregated cells of the first group. In an example implementation, the cells in the second group may be have their own limitations with respect to simultaneous reception and transmission in the aggregated cells of the second group. Cells in different licensed bands may have their own constraints on simultaneous reception and transmission in the aggregated cells.

In an implementation, cells may be grouped according to their limitations on simultaneous reception and transmission in the aggregated cells.

In an example embodiment, a UE may not assume that LAA cells may follow the same uplink and downlink subframes as the PCell. A PCell may employ frame structure Type 1 or 2, while an LAA cell may employ frame structure Type 3. In an example embodiment, constraints are introduced for a UE and/or eNB for cells in a group to reduce the transmit and/or receive possibilities. This may reduce unnecessary signal processing in the UE and/or eNB. The constraints may be employed by the UE and/or eNB to reduce battery power consumption in the UE and/or eNB. The constraints may be applicable to the cells within a cell group, for example, the cells in the licensed band, a first group of cells in an unlicensed band A, a second group of cells in an unlicensed band B, etc. Example embodiments improve LAA cell efficiency and reduces UE battery power consumption and reduces UE processing requirements.

In an example embodiment, cells may be grouped based on simultaneous reception and transmission in the aggregated cells in a group. A UE may not be capable of simultaneous reception and transmission in the aggregated cells within a cell group.

In an example embodiment, a UE may transmit an RRC message (e.g. UE capability message) to the eNB. The message may comprise one or more parameters indicating the UE capability with respect to the example cell grouping. For example, the one or more parameters may indicate certain frequency bands, in which cells are grouped within a cell group. For example, the one or more parameters may comprise a set of frequencies that are in a cell group. For example, the one or more parameters may be a transceiver parameter in the UE indicating the frequency bands in which cells may be grouped. For example, the one or more parameters may indicate a device category or certain capability that indicate the limitation on cell aggregation to the UE.

In an example, such an aggregation limitation in different cell groups may be a characteristic of the UE, and an eNB may not be informed about such limitation. In an example embodiment, the aggregation limitation may be pre-specified in both eNB and UE based on bands, cell frequencies, cell bandwidth, and/or other parameters.

In an example, an eNB may configure the cell grouping in the UE. An eNB may transmit one or more messages to the UE configuring cell grouping based on simultaneous reception and transmission capability in the aggregated cells within a cell group. For example, an eNB may transmit one or more RRC messages comprising cell indexes of a cell group (e.g. identified by a group index). The one or more RRC message may associate the cells with a group, e.g. using a cell group index.

In an example embodiment, a cell in a group may be considered a lead cell. A lead cell may be preconfigured by an RRC message. An RRC message may comprise one or more parameters, e.g. a cell index, of a cell in a cell group. In an example, an RRC may comprise one or more configuration parameters for an SCell that implicitly or explicitly indicates that the cell is a lead cell in a group. In an example, the lead cell may be determined according to a predefined rule, for example the cell with a lowest cell index, and/or the like. The predefined rule may be configured in a UE and/or an eNB.

In an example embodiment, the lead cell may be identified by a UE on a subframe by subframe basis. In an example embodiment, there is no need to select a lead cell, and a collective constraint may be applied to the cells in a group at any moment. In an example, the cell that has certain characteristics at a moment (e.g. eNB is transmitting, UE is transmitting) may determine the status of other cells. In an example, a lead cell may be any cell in a cell group.

In an example implementation, when a UE is not capable of receiving downlink signals in a group at certain time, the UE may not decode downlink signals of cells of a group at that certain time. The UE may not blind decode the downlink cell and/or search for downlink signals. The UE may not expect to receive and monitor downlink signals such as synchronization signals, DRS, control channels (PCFICH, PDCCH, ePDCCH, PDSCH, and/or CRS, etc). This may reduce the battery power consumption in the UE, since the UE may not decode the receive signals. For example, the UE may turn off the receiver on one or more cells in a group. The UE may selectively monitor downlink signals/channels of a subframe based on downlink and uplink transmissions in another cell in the group.

An example scenario is described below. The lead cell may be any one of the activated cells within a group.

Example status of a lead cell in a group: downlink transmission, then example UE capability in other cells of the group may be one or more of the following: Can receive downlink signals; Cannot transmit uplink signals; Can perform LBT for uplink transmission; UE may be during a guard period (e.g. DL to UL transition period).

Example status of a lead cell in a group: idle (no DL/UL transmission), then Example UE capability in other cells of the group may be one or more of the following: Can receive downlink signals; Can transmit uplink signals; Can perform LBT for uplink transmission; UE may be during a guard period (e.g. DL to UL transition period, or UL to DL transition period).

Example status of a lead cell in a group: Uplink transmission, then Example UE capability in other cells of the group may be one or more of the following: Cannot receive downlink signals; Can transmit uplink signals; Can perform LBT for uplink transmission (e.g. with a different threshold); UE may be during a guard period (e.g. UL to DL transition period).

In an example, the lead cell may be any one of the activated cells within a group. In the following examples, the state of a full subframe is described.

Status of a lead cell during the full subframe n: downlink transmission, then UE capability in other cells of the group may be one or more of the following: Subframe n can be downlink; Subframe n can be an ending (partial) uplink subframe (e.g. depending on configuration); subframe n+1 can be a beginning (partial) uplink subframe (e.g. depending on configuration); Can perform LBT for uplink transmission for a beginning (partial) uplink subframe in subframe n+1 (e.g. depending on configuration); UE may be during a guard period (e.g. DL to UL transition period).

Status of a lead cell during the full subframe n: idle period, then UE capability in other cells of the group may be one or more of the following: Can receive downlink signals; Can transmit uplink signals; Can perform LBT for uplink transmission; UE may be during a guard period (e.g. DL to UL transition period, or UL to DL transition period).

Status of a lead cell during the full subframe n: uplink transmission, then UE capability in other cells of the group may be one or more of the following: Can receive downlink reservation signals during an end period of subframe n, can receive downlink beginning partial subframe (e.g. depending on configuration, and/or N_TA); Can transmit uplink signals; Can perform LBT for uplink transmission (e.g. with a different threshold); UE may be during the guard period (e.g. UL to DL transition period).

For example, when subframe n is a full downlink subframe, a UE may receive downlink signals in other cells of the cell group in subframe n. Depending on implementation, subframe n may be capable of being an ending (partial) uplink subframe (e.g. depend on TA values and/or whether implementation of ending partial uplink subframe is allowed). Subframe n+1 can be a beginning (partial) uplink subframe (e.g. depend on TA values and/or whether implementation of beginning partial uplink subframe is allowed). For example, in an implementation the second slot of subframe n+1 may be employed for uplink transmission. In an example, if a UE transmitting signals in full subframe k in a cell in response to a grant, the UE may not monitor downlink control channels in subframe k on other cells.

In an example embodiment, a detected downlink burst may determine the status of the cells in a group. For example, when a UE starts receiving a downlink burst in a subframe, the UE may assume that the cells in the group are in downlink transmission mode, until the last downlink transmission burst on the last cell ends. The UE may not transmit any signals until the downlink transmission from the eNB continues. After the UE detects the last downlink transmission on one or the cells, the UE may start LBT for uplink transmission (e.g. if the UE has an uplink grant, or needs to transmit an SRS, PRACH, etc).

In an example, when a UE starts transmission of an uplink burst in a subframe, the UE may assume that the cells are in uplink transmission mode, until the last uplink TB is transmitted on a last cell. During the uplink transmission on a cell, the UE may not monitor downlink signals on other cells until uplink transmission on a last cell ends. For example, the UE may not monitor downlink control channel, synch signal, DRS and other downlink signals on a cell when the UE is transmitting on another cell in the group.

When a subframe is a partial subframe, the status of other cells in the subframe and subsequent subframes may depend on the duration of the transmission during the partial subframe and whether the partial subframe is a beginning subframe or an ending subframe. Some example scenarios are described below.

Status of a lead cell during a partial subframe n: downlink end partial transmission, then UE capability in other cells of the group may be one or more of the following: Subframe n can be downlink, Subframe n can be an ending (partial) uplink subframe (e.g. depending on configuration, and/or N_TA), subframe n+1 can be a beginning (partial or full) uplink subframe (e.g. depending on partial subframe length, configuration, and/or N_TA), Can perform LBT for uplink transmission for a beginning (partial or full) uplink subframe (e.g. depending on partial subframe length, configuration, and/or N_TA), UE may be during a guard period (e.g. DL to UL transition period).

Status of a lead cell during a partial subframe n: downlink beginning partial transmission, then UE capability in other cells of the group may be one or more of the following: Subframe n can be downlink; Subframe n can be an ending (partial) uplink subframe, subframe n+1 can be a beginning (partial) uplink subframe or no uplink (e.g. depending on partial subframe length, configuration, and/or N_TA).

In an example embodiment, similar constraints may be applied to eNB. This process may reduce battery power consumption in the eNB. Groupings may provide scheduling constraints in the eNB for downlink transmission and uplink reception similar to the constraints in the UE.

Some example embodiments are shown in FIGS. 12 to 15. In example figures, a limited number of downlink bursts and uplink bursts are shown. In an example, an uplink burst or downlink burst may be one or more transmission bursts.

In an example embodiment as shown in FIG. 12, downlink transmission may start at the same or different starting time in different cells (e.g. depending on scheduling, LBT, configuration, etc.). For example, LBT may detect an interference in cell2 until the start of DL2 burst, and LBT in cell1 indicate a clear channel earlier. For example, eNB may start scheduling downlink information on cell2 later than cell 1. The eNB may transmit downlink signals and UE may receive downlink signals until the last downlink burst in a cell is ended, e.g. DL3 (the UE is in downlink mode). Then the UE may start uplink transmission, if UE is granted uplink resources. In an example, the UE may transmit uplink until the last uplink burst is ended, e.g. UL3 (the UE is in uplink mode). The UE may not transmit any signal when it is in downlink mode. The UE may not receive any signal and may not decode downlink control signals when it is in uplink mode. FIG. 12 is an example, in some scenarios, some of the cells may not be scheduled for downlink or uplink transmission. For example, consider FIG. 12 and when DL2 or UL1 may not be transmitted.

Another example is shown in FIG. 13. FIG. 13 illustrates a scenario, wherein LAA cell 1 transmits two downlink bursts. In FIG. 13, LAA cell 1 is the cell with a downlink that last longer.

In an example embodiment as shown in FIG. 14, downlink bursts on one or more cells may end substantially at the same time, and/or in the same subframe. In an example the downlink burst that started first may determine when the COT is ended. In an example, this cell may be the lead cell. Other downlink transmission bursts may start later (DL2 and DL3), but may end at the same time as DL1 or earlier than DL1 (e.g. when there is no data to be transmitted on DL3, DL3 may end earlier). In an example, the same concept may apply to uplink transmissions. The uplink burst that started first may determine the beginning of an uplink burst. The COT may be determined from the time that UL1 has started and may end when UL2/UL3 is ended.

In an example embodiment as shown in FIG. 15, downlink and/or uplink transmission on multiple cells may start at the same time. For example, the eNB may start downlink transmission on multiple cells, when LBT clears on one or more cells. For example, in the figures DL1, DL2, and DL3 started at the same time. In an example, if LBT of a cell does not indicate clear channel, the eNB may not transmit a downlink signal on the cell. In an example, if LBT of a cell does not indicate a clear channel, the eNb may defer transmission on other cell for certain period. In an example, eNB may decide on whether it should defer transmission on cells or transmit on some of the cells and not to transmit on some other cells. The downlink bursts may end at different times, depending on scheduling method and available downlink data. The same may apply to uplink. For example, UL1 and UL3 started at the same time, but may end at different times. The eNB may not have scheduled data for cell2 in the uplink, or LBT in the UE may not have indicated a clear channel

In an example embodiment, a cell may be configured or selected as a lead cell, and other cells in a group may follow the status of the lead cell. In an example embodiment, one or more RRC message may comprise one or more parameters indicating the configuration parameters of downlink and uplink transmission parameter and may determine one or more modes as described above is operated by a UE and/or eNB.

In an example embodiment, the examples in FIG. 12 to FIG. 15 may be extended to illustrate the operations of an eNB. For example, an eNB may not decode signals from a UE, when it is in a downlink transmission mode. For example, an eNB may not transmit any signals to any UE, when it is in the receive mode. The constraints described in the example embodiments may be extended to the operations on an eNB. The constraints may be employed by an eNB scheduler to schedule uplink and downlink TBs. for example, an eNB may not schedule uplink TB on cell1 and downlink TB on cell 1.

Example embodiments may be deployed to resolve conflicting situations in a UE. For example, when a UE is scheduled to transmit a TB in subframe n, but the UE receives indication of downlink eNB signals in subframe n-1 and/or subframe n, the UE may decide to ignore the downlink signal or transmit the uplink grant. In an example embodiment, the UE may consider that downlink transmission from an eNB may have priority over uplink transmission from the UE. For example, when the UE detects downlink transmission for an eNB in subframe n, the UE may consider that the subframe n is a downlink subframe. The UE may ignore conflicting uplink grants and ignore a scheduled uplink transmission (e.g. SRS, data, control, PRACH, etc). In an example, when eNB has already started uplink transmission, it may not be able to detect downlink signals transmitted from the UE during its uplink transmission in the cell group.

In an example embodiment, an eNB may schedule downlink and uplink TBs according to the constraints described in the embodiment. The UE may transmit or receive signals according to the (e)PDCCH scheduling grants received from the eNB. The UE and/or eNB may employ the constraints described in the example embodiment to reduce the required processing of signals and reduce battery power consumption.

A UE and/or eNB may configure a timer and/or a counter tracking the continuous transmission in a burst. A UE and/or eNB may start the timer when it starts transmission and/or reception. This may allow the UE and/or an eNB when an uplink and/or downlink transmission burst may end. The UE and/or eNB may subsequently base its downlink and/or uplink processing based on the value in the timer. An eNB and/or UE may be allowed to continuously transmit up to a maximum duration. In an example embodiment, an eNB may transmit an RRC message to a UE comprising the value of the timer/counter.

According to various embodiments, a device such as, for example, a wireless device, a base station and/or the like, may comprise one or more processors and memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. Embodiments of example actions are illustrated in the accompanying figures and specification.

FIG. 17 is an example flow diagram as per an aspect of an embodiment of the present disclosure. At 1710, a wireless device may receive one or more radio resource control (RRC) messages. The at least one RRC message may comprise configuration parameters for a first licensed assisted access (LAA) cell and a second LAA cell. At 1720, the wireless device may selectively monitor, in a first subframe, a downlink physical control channel (PDCCH) on the first LAA cell, depending on whether there is an uplink transmission in the first subframe on the second LAA cell.

The (selectively) monitoring may not occur when, for example, the uplink transmission is in the first subframe on the second LAA cell. The uplink transmission may be, for example, a physical uplink shared channel (PUSCH) transmission. The PDCCH may be, for example, an enhanced PDCCH. According to an embodiment, the first LAA cell and the second LAA cell may belong to a first cell group. The first cell group may comprise a plurality of cells that operate, for example, in a first frequency band. The one or more RRC messages may further comprise, for example, one or more configuration parameters of the first cell group. The first subframe for the second LAA cell may be, for example, a partial uplink subframe. The first subframe for the second LAA cell may be, for example, may be a full uplink subframe. The first LAA cell and the second LAA cell may operate according to frame structure Type 3.

FIG. 18 is an example flow diagram as per an aspect of an embodiment of the present disclosure. At 1810, a wireless device may receive one or more radio resource control (RRC) messages. The at least one RRC message may comprise configuration parameters for a first cell and a LAA cell. At 1820, the wireless device may selectively monitor, in a first subframe, a downlink physical control channel (PDCCH) on the cell, depending on whether there is an uplink transmission in the first subframe on the LAA cell.

FIG. 19 is an example flow diagram as per an aspect of an embodiment of the present disclosure. At 1910, a base station may transmit one or more radio resource control (RRC) messages. The at least one RRC message may comprise configuration parameters for a first licensed assisted access (LAA) cell and a second LAA cell. At 1920, the base station may selectively transmit, in a first subframe, a downlink physical control channel (PDCCH) on the first LAA cell, depending on whether there is an uplink transmission in the first subframe on the second LAA cell.

In this specification, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” In this specification, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell, cell2}.

In this specification, parameters (Information elements: IEs) may comprise one or more objects, and each of those objects may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J, then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an isolatable element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e hardware with a biological element) or a combination thereof, all of which are behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. Finally, it needs to be emphasized that the above mentioned technologies are often used in combination to achieve the result of a functional module.

The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments. In particular, it should be noted that, for example purposes, the above explanation has focused on the example(s) using FDD communication systems. However, one skilled in the art will recognize that embodiments of the disclosure may also be implemented in a system comprising one or more TDD cells (e.g. frame structure 2 and/or frame structure 3-licensed assisted access). The disclosed methods and systems may be implemented in wireless or wireline systems. The features of various embodiments presented in this disclosure may be combined. One or many features (method or system) of one embodiment may be implemented in other embodiments. Only a limited number of example combinations are shown to indicate to one skilled in the art the possibility of features that may be combined in various embodiments to create enhanced transmission and reception systems and methods.

In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 112. 

1. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages comprising configuration parameters for a first cell in an unlicensed spectrum and a second cell in the unlicensed spectrum; receiving a downlink transmission via the second cell; and based on the downlink transmission via the second cell, selectively monitoring a physical downlink control channel (PDCCH) during a time duration for the first cell.
 2. The method of claim 1, wherein the downlink transmission is a physical downlink shared channel (PDSCH) transmission.
 3. The method of claim 1, wherein the PDCCH is an enhanced PDCCH.
 4. The method of claim 1, wherein the first cell and the second cell belong to a cell group.
 5. The method of claim 4, wherein the cell group comprises a plurality of cells that operate in a same frequency band of the unlicensed spectrum.
 6. The method of claim 4, wherein the one or more RRC messages further comprise one or more configuration parameters of the cell group.
 7. The method of claim 1, wherein the time duration is a subframe.
 8. The method of claim 1, wherein receiving the downlink transmission comprises receiving the downlink transmission during a partial downlink subframe or a full downlink subframe.
 9. The method of claim 1, wherein the first cell and the second cell operate according to frame structure Type
 3. 10. The method of claim 1, further comprising based on a downlink transmission not occurring during a second time duration for the second cell, monitoring the PDCCH during a time duration for the first cell.
 11. The method of claim 1, wherein the one or more RRC messages indicate a cell grouping at the wireless device.
 12. The method of claim 1, wherein the one or more RRC messages indicate a cell group index of a cell group comprising the first cell and the second cell.
 13. The method of claim 1, wherein the selectively monitoring comprises: monitoring the PDCCH based on a first condition; and skipping monitoring of the PDCCH based on a second condition.
 14. The method of claim 13, wherein: the first condition comprises no uplink transmission during the time duration; and the second condition comprises an uplink transmission during the time duration.
 15. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive one or more radio resource control (RRC) messages comprising configuration parameters for a first cell in an unlicensed spectrum and a second cell in the unlicensed spectrum; receive a downlink transmission via the second cell; and based on the downlink transmission via the second cell, selectively monitor a physical downlink control channel (PDCCH) during a time duration for the first cell.
 16. The wireless device of claim 15, wherein the downlink transmission is a physical downlink shared channel (PDSCH) transmission.
 17. The wireless device of claim 15, wherein the PDCCH is an enhanced PDCCH.
 18. The wireless device of claim 15, wherein the first cell and the second cell belong to a cell group.
 19. The wireless device of claim 18, wherein the cell group comprises a plurality of cells that operate in a same frequency band of the unlicensed spectrum.
 20. The wireless device of claim 18, wherein the one or more RRC messages further comprise one or more configuration parameters of the cell group.
 21. The wireless device of claim 15, wherein the time duration is a subframe.
 22. The wireless device of claim 15, wherein the instructions, when executed, cause the wireless device to receive the downlink transmission at least by receiving the downlink transmission during a partial downlink subframe or a full downlink subframe.
 23. The wireless device of claim 15, wherein the first cell and the second cell operate according to frame structure Type
 3. 24. The wireless device of claim 15, wherein the instructions, when executed, further cause the wireless device to, based on a downlink transmission not occurring during a second time duration for the second cell, monitor the PDCCH during a time duration for the first cell.
 25. The wireless device of claim 15, wherein the one or more RRC messages indicate a cell grouping at the wireless device.
 26. The wireless device of claim 15, wherein the one or more RRC messages indicate a cell group index of a cell group comprising the first cell and the second cell.
 27. The wireless device of claim 15, wherein the instructions, when executed, cause the wireless device to selectively monitor the PDCCH at least by: monitoring the PDCCH based on a first condition; and skipping monitoring of the PDCCH based on a second condition.
 28. The wireless device of claim 27, wherein: the first condition comprises no uplink transmission during the time duration; and the second condition comprises an uplink transmission during the time duration.
 29. A non-transitory computer-readable medium storing instructions that, when executed configure a wireless device to: receive one or more radio resource control (RRC) messages comprising configuration parameters for a first cell in an unlicensed spectrum and a second cell in the unlicensed spectrum; receive a downlink transmission via the second cell; and based on the downlink transmission via the second cell, selectively monitor a physical downlink control channel (PDCCH) during a time duration for the first cell.
 30. The non-transitory computer-readable medium of claim 29, wherein the downlink transmission is a physical downlink shared channel (PDSCH) transmission.
 31. The non-transitory computer-readable medium of claim 29, wherein the PDCCH is an enhanced PDCCH.
 32. The non-transitory computer-readable medium of claim 29, wherein the first cell and the second cell belong to a cell group.
 33. The non-transitory computer-readable medium of claim 32, wherein the cell group comprises a plurality of cells that operate in a same frequency band of the unlicensed spectrum.
 34. The non-transitory computer-readable medium of claim 32, wherein the one or more RRC messages further comprise one or more configuration parameters of the cell group.
 35. The non-transitory computer-readable medium of claim 29, wherein the time duration is a subframe.
 36. The non-transitory computer-readable medium of claim 29, wherein the instructions, when executed, configure the wireless device to receive the downlink transmission at least by receiving the downlink transmission during a partial downlink subframe of a full downlink subframe.
 37. The non-transitory computer-readable medium of claim 29, wherein the first cell and the second cell operate according to frame structure Type
 3. 38. The non-transitory computer-readable medium of claim 29, wherein the instructions, when executed, further configure the wireless device to, based on a downlink transmission not occurring during a second time duration for the second cell, monitor the PDCCH during a time duration for the first cell.
 39. The non-transitory computer-readable medium of claim 29, wherein the one or more RRC messages indicate a cell grouping at the wireless device.
 40. The non-transitory computer-readable medium of claim 29, wherein the one or more RRC messages indicate a cell group index of a cell group comprising the first cell and the second cell.
 41. The non-transitory computer-readable medium of claim 29, wherein the instructions, when executed, configure the wireless device to selectively monitor the PDCCH at least by: monitoring the PDCCH based on a first condition; and skipping monitoring of the PDCCH based on a second condition.
 42. The non-transitory computer-readable medium of claim 41, wherein: the first condition comprises no uplink transmission during the time duration; and the second condition comprises an uplink transmission during the time duration. 